Conversation
Member
Author
|
This branch is now based on |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Goal
The goal is to export all the data fetched from GitHub into a database, with history, so that can access the data easily and quickly, and explore the evolution of the data.
Implementation
I'm using Hasura on top of Postgres to define the SQL schema as well as expose a GraphQL API to insert and read the data easily.
Instead of modifying the existing code to insert to postgres instead of writing JSON files, I've written a separate code file
hasura.jsthat reads the JSON files generated byindex.jsand loads them into postgres. All of the data is inserted into postgres using one big GraphQL query. Each time, the entire data graph is inserted as new entities in order to keep older entities intact.How to load up the data into Postgres
.envand fillGITHUB_ID,GITHUB_OAUTHandGITHUB_ORGAnpm start generatedocker-compose up -dHASURA_ADMIN_SECRET=hasuraandHASURA_GRAPHQL_URL=http://localhost:8080/v1/graphqlto.envnode -r dotenv/config src/hasura.jsExamples of queries
Once the data is loaded up, browser to
http://localhost:8080(password ishasura). In the GraphiQL tab, we can test some GraphQL queries:History of the number of repositories for a member
{ "data": { "member": [ { "organization": { "fetched_at": "2019-10-30T15:08:32.387283+00:00" }, "repositories_aggregate": { "aggregate": { "count": 2 } } }, { "organization": { "fetched_at": "2019-10-30T15:03:46.044145+00:00" }, "repositories_aggregate": { "aggregate": { "count": 2 } } }, { "organization": { "fetched_at": "2019-10-30T14:55:38.577492+00:00" }, "repositories_aggregate": { "aggregate": { "count": 1 } } } ] } }History of contributions of a member
{ "data": { "member": [ { "organization": { "fetched_at": "2019-11-01T22:19:37.413963+00:00" }, "contribution_stats": { "total_commit_contributions": 2, "total_issue_contributions": 3, "total_pull_request_contributions": 4, "total_pull_request_review_contributions": 0, "total_repository_contributions": 4 } }, { "organization": { "fetched_at": "2019-11-01T22:00:26.591278+00:00" }, "contribution_stats": { "total_commit_contributions": 2, "total_issue_contributions": 3, "total_pull_request_contributions": 4, "total_pull_request_review_contributions": 0, "total_repository_contributions": 4 } } ] } }Improvements to make
fetched_atfield that is currently on the organization entity and that denote the time that data was fetched, needs to be moved to its own entity.